The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Identify game component assets
|
|
Obtain project brief and documents Completed |
Evidence:
|
Identify game-production assets required to meet creative and production requirements and technical specifications Completed |
Evidence:
|
Discuss formats of assets and issues of asset integration and with appropriate personnel Completed |
Evidence:
|
Save all digital assets in the appropriate format for inclusion, and store for retrieval Completed |
Evidence:
|
Determine sequence for development of beta version prototype for testing game play Completed |
Evidence:
|
Create a schedule for production and testing Completed |
Evidence:
|
Determine strategies for monitoring production progress against schedule Completed |
Evidence:
|
Identify capability of game-engine software and tools and make selection
|
|
Identify and review the range of industry standard game-engine software and development tools available Completed |
Evidence:
|
Assess the software and tools related to specified game concepts and play requirements Completed |
Evidence:
|
Discuss considerations for selection of game-engine software with relevant personnel to ensure selection will meet specified outcomes Completed |
Evidence:
|
Select game-engine software Completed |
Evidence:
|
Use game-engine software
|
|
Load game engine, including sound and game play Completed |
Evidence:
|
Create a new file for the specified task and name appropriately Completed |
Evidence:
|
Display and use tools and features of software relevant to the game production process Completed |
Evidence:
|
Create custom code to achieve a unique function Completed |
Evidence:
|
Create game-play sequence and prototype
|
|
Import and assemble game-play assets in appropriate sequence according to creative and technical requirements Completed |
Evidence:
|
Create and check game-play elements according to creative and technical requirements Completed |
Evidence:
|
Test and run game-play sequence as a presentation to ensure the sequence meets creative, production and technical requirements Completed |
Evidence:
|
Export to game engine and create prototype Completed |
Evidence:
|
Save file formats and identify for specified purpose Completed |
Evidence:
|
Evaluate game prototype
|
|
Demonstrate initial prototype to relevant personnel Completed |
Evidence:
|
Evaluate against criteria, including achievement of a creative and user-friendly product Completed |
Evidence:
|
Discuss and agree on required changes Completed |
Evidence:
|
Assist if required in tests and user trials Completed |
Evidence:
|
Evaluate feedback from user trials Completed |
Evidence:
|
Confirm endorsement from relevant personnel to develop prototype into complete product Completed |
Evidence:
|
Transform prototype into final proof of concept prototype
|
|
Make necessary changes as indicated by user trials Completed |
Evidence:
|
Integrate all game elements as required by specifications Completed |
Evidence:
|
Make final checks to ensure all sequences conform to the navigation design Completed |
Evidence:
|
Save into specified storage systems Completed |
Evidence:
|